|
Dependency hell is a colloquial term for the frustration of some software users who have installed software packages which have dependencies on specific versions of other software packages. The dependency issue arises around ''shared'' packages/libraries on which several other packages have dependencies but where they depend on different and incompatible versions of the shared packages. If the shared package/library can only be installed in a single version, the user/administrator may need to address the problem by obtaining newer/older versions of the dependent packages. This, in turn, may break other dependencies and push the problem to another set of packages, thus the term ''hell''. == Overview == Often, rather than "reinventing the wheel", software is designed to take advantage of other software components that are already available, or have already been designed and implemented for use elsewhere. This could be compared to how people building a house might buy off-the-shelf components, such as bricks, windows, and doors, rather than producing ''everything'' themselves. Even for a builder, it can be a problem if a building is designed for a certain door type, and only doors with different specifications are available. However, in the software world, where components evolve rapidly and depend significantly on one another, this problem becomes more pronounced.〔 The issue of dependency hell may be regarded as an anti-pattern, where the fault lies less with the suppliers of the products than with the framework into which they have to fit. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「dependency hell」の詳細全文を読む スポンサード リンク
|